Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@PLUGINS.md`:
- Around line 118-127: Update the Confluence create-from-jira command
documentation to include "decision-record" as a valid --type option: add
decision-record to the Synopsis line in PLUGINS.md where the create-from-jira
command lists `design-doc|feature-spec|runbook`, and apply the same change to
the create-from-jira docs by updating the argument-hint frontmatter and the
Synopsis code block in plugins/confluence/commands/create-from-jira.md so the
--type values read `design-doc|feature-spec|runbook|decision-record`
consistently.

In `@plugins/confluence/commands/sync-meeting-notes.md`:
- Around line 118-138: Add blank lines before and after each Markdown table to
satisfy MD058 by inserting an empty line above the "Arguments" table (the table
under the "## Arguments" heading) and an empty line below it, and likewise
insert an empty line above and below the "Error Handling" table (the table under
the "## Error Handling" heading); ensure both tables are separated from
surrounding headings and paragraphs by one blank line each so markdownlint no
longer flags them.
- Around line 10-12: Add a language specifier to the fenced code block that
shows the command usage for /confluence:sync-meeting-notes so the static
analyzer stops flagging it; locate the fence containing
"/confluence:sync-meeting-notes <space-key> <title> [--parent-id <id>] [--update
<page-id>]" and change the opening triple backticks to include a language token
such as "text" or "bash" (e.g., ```text).
- Around line 89-98: Replace the hardcoded label name in the
mcp__mcp-atlassian__confluence_add_label call: do not pass the literal
"meeting-2026-05"; instead use a dynamic label like "meeting-<YYYY-MM>" and
update the surrounding prose to instruct computing the current year-month at
runtime (derive from current date/time in the runtime language before calling
mcp__mcp-atlassian__confluence_add_label so each page gets a label based on the
actual meeting date).
- Around line 100-116: Add a language specifier ("bash" or "shell") to each of
the three fenced code blocks in the Usage Examples so markdownlint MD040 is
satisfied; specifically update the three blocks containing the shell commands
(/jira:grooming ... /confluence:sync-meeting-notes ...) so their opening fences
read ```bash instead of ``` for the examples that include the /jira:grooming and
the two /confluence:sync-meeting-notes commands.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/data.json`:
- Around line 1808-1813: Update the "description" field for the command named
"sync-meeting-notes" in the data.json entry so it explicitly states where the
meeting content is sourced from (e.g., conversation context, grooming output, or
files). Locate the object with "name": "sync-meeting-notes" and replace the
current description value with a clarified sentence such as "Publish meeting
notes or agendas from conversation context (or grooming output or files) to
Confluence with structured formatting" to improve discoverability.

In `@plugins/confluence/commands/create-from-jira.md`:
- Line 3: Update the user-facing `--type` option list in the command argument
hints to include the missing `decision-record` entry; specifically modify the
`argument-hint` occurrences in create-from-jira.md so the `--type` choices read
"design-doc|feature-spec|runbook|decision-record" (update both places where the
hint appears, e.g., the top-level `argument-hint` and the later occurrence
around line 11) to keep the displayed syntax consistent with the command
description and allowed arguments.
- Around line 10-12: The markdown in
plugins/confluence/commands/create-from-jira.md has unlabeled fenced code blocks
and tables without surrounding blank lines; update each fenced block (e.g., the
command usage block "/confluence:create-from-jira <issue-key> [...]") to include
an appropriate language tag such as bash or text to satisfy MD040/MD058, and
ensure every table block has a blank line before and after it (matching the
format used in plugins/hello-world/commands/echo.md); apply these fixes
consistently to all affected sections mentioned in the review so the linter
passes.

In `@plugins/confluence/commands/search.md`:
- Around line 10-12: The command docs for /confluence:search currently fail
markdownlint MD040/MD058 because the usage code block lacks a fenced language
and the Arguments/Error Handling tables need surrounding blank lines; update the
usage block to use a fenced language (e.g., ```bash) and add a blank line before
and after each table (Arguments, Error Handling) for the /confluence:search
command and the other affected sections (lines referenced 64-74, 81-98, 101-105,
113-117), matching the structure used in plugins/hello-world/commands/echo.md so
the linter passes.

In `@plugins/confluence/evals/sync-meeting-notes.yaml`:
- Around line 41-44: The example meeting-note lines contain real person names;
update the fixture in sync-meeting-notes.yaml to use role-based placeholders
instead (e.g., replace "Attendees: Alice, Bob, Carol" with "Attendees: Product
Manager, Backend Engineer, Designer", change "Discussion: finalize architecture
decision for release" to remain but ensure roles are used in actions and
decisions such as "Actions: Backend Engineer to update the design doc", and
likewise replace any other named references in the same block so all
attendees/action owners are roles rather than personal names.

In `@plugins/confluence/skills/confluence-conventions/SKILL.md`:
- Around line 40-47: Two Markdown tables (one starting with the header "|
Content Type | Required Labels | Optional Labels |" and the other the second
table referenced in the comment) lack surrounding blank lines and trigger MD058;
fix by adding a single blank line both immediately before and immediately after
each table so each table is separated from surrounding paragraphs and headings.
Ensure you update the blocks that include the "| Content Type | Required Labels
| Optional Labels |" header and the other table block so there is exactly one
blank line above and one blank line below each table.

In `@plugins/confluence/skills/page-templates/SKILL.md`:
- Around line 162-163: The example uses real-person names; replace them with
neutral role-based placeholders. In SKILL.md update the sample meeting lines
that read "Attendees: Alice, Bob, Carol" and "Facilitator: Alice" (and the
similar occurrence at the later block) to role placeholders such as "Attendees:
Product Manager, Engineer, Designer" and "Facilitator: Product Manager" (or
"Attendee 1, Attendee 2, Attendee 3" / "Facilitator: Attendee 1") so no real
names appear.

---

Nitpick comments:
In `@plugins/confluence/commands/search.md`:
- Around line 33-35: The Raw-CQL detection rule that treats presence of
"AND"/"OR" as sufficient should be tightened in the search parsing logic (the
function that decides "raw CQL" / "pass-through", e.g., isRawCql or detectRawCql
used in the Confluence query parser) by requiring explicit CQL field/operator
patterns before allowing pass-through; update the check to only classify as raw
CQL when the input contains CQL-style tokens such as a field+operator pattern
(examples: "field =", "field ~", "field :", or "field IN") or matches a regex
like <field>\s*(=|~|:|IN)\s*<value>, while still allowing Jira-key detection and
natural-language fallback otherwise.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@plugins/confluence/evals/sync-meeting-notes.yaml`:
- Around line 45-51: Add an assertion to verify a successful Confluence API
interaction in the existing assert block (which currently contains icontains
checks for "meeting notes", "Attendees", and "Action items"). For example, add
an icontains or regex assertion that looks for a success message or page URL
(e.g., "Page created", "Page updated", or a Confluence URL pattern like
"confluence" or "atlassian.net") in the command output to confirm the page was
actually created/updated rather than just containing text fragments.